Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Now cregex "appears" to be included (for backward compatibility) #1176

Merged
merged 5 commits into from
Jan 16, 2025

Conversation

Iximiel
Copy link
Member

@Iximiel Iximiel commented Jan 16, 2025

Description

Note

rt-coverage-antibetarmsd fails due to what is being solved here #1166

As what's told in #1175 I'm pushing a couple of commit that should solve the backward compatibility with "absence" of cregex.

In the first two I declare that cregex is there in config.txt (plumed config has cregex) and in PLMD::config::hasCregex()

Target release

I would like my code to appear in release v2.10

Type of contribution
  • changes to code or doc authored by PLUMED developers, or additions of code in the core or within the default modules
  • changes to a module not authored by you
  • new module contribution or edit of a module authored by you
Copyright
  • I agree to transfer the copyright of the code I have written to the PLUMED developers or to the author of the code I am modifying.
  • the module I added or modified contains a COPYRIGHT file with the correct license information. Code should be released under an open source license. I also used the command cd src && ./header.sh mymodulename in order to make sure the headers of the module are correct.
Tests
  • I added a new regtest or modified an existing regtest to validate my changes.
  • I verified that all regtests are passed successfully on GitHub Actions.

@Iximiel Iximiel force-pushed the fix2.10/phantomcregex branch from d72d0ed to 06c2cbd Compare January 16, 2025 11:33
@Iximiel
Copy link
Member Author

Iximiel commented Jan 16, 2025

I rebased on the current v2.10 because #1166 is now merged, so the tests should pass

I also added a test to check the "phantom" cregex with a comment that explain why it is there (and ran astyle because I forgot that...)

@carlocamilloni
Copy link
Member

I am merging it and then we can reduce the numerical precision of that single failing test

@carlocamilloni carlocamilloni merged commit e2a1dc0 into plumed:v2.10 Jan 16, 2025
16 of 18 checks passed
@Iximiel
Copy link
Member Author

Iximiel commented Jan 16, 2025

I am merging it and then we can reduce the numerical precision of that single failing test

I do no think there is a need to do that: the CI looks like is passing with no problems(apart the usual mac one)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants